Skip to content

fix: add Overview submodule for v13 module overview compatibility#94

Merged
CybotTM merged 1 commit intomainfrom
fix/v13-module-overview
Mar 2, 2026
Merged

fix: add Overview submodule for v13 module overview compatibility#94
CybotTM merged 1 commit intomainfrom
fix/v13-module-overview

Conversation

@CybotTM
Copy link
Member

@CybotTM CybotTM commented Mar 1, 2026

Summary

  • Adds an explicit admin_vault_overview submodule as the first child of the admin_vault parent module
  • Uses position => ['before' => '*'] to ensure it appears first in the module menu
  • In TYPO3 v13, clicking a parent module with dependsOnSubmodules => true auto-redirects to the first submodule — this fix ensures users land on the Overview page instead of the Secrets submodule
  • In TYPO3 v14, showSubmoduleOverview => true handles this natively, so the new submodule simply becomes an additional entry

Problem

TYPO3 v14 introduced showSubmoduleOverview which renders a module overview page when clicking the parent module. In v13, this feature doesn't exist — instead, dependsOnSubmodules => true causes an auto-redirect to the first registered submodule. Without an explicit Overview submodule, users were redirected directly to Secrets, never seeing the overview dashboard.

Test plan

  • In TYPO3 v13: Click "Vault" in backend sidebar → should show Overview page with statistics and Quick Start guide
  • In TYPO3 v14: Click "Vault" in backend sidebar → should still show module overview (via native showSubmoduleOverview)
  • In v14: "Overview" tab should appear as first item in module menu
  • Verify all other submodules (Secrets, Key Pairs) still work

In TYPO3 v13, showSubmoduleOverview is not supported and the parent module
redirects to the first submodule. Add an explicit Overview submodule as the
first child so v13 shows the overview/dashboard page instead of the Secrets
list.

Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a compatibility issue in TYPO3 v13 where clicking a parent module with submodules would automatically redirect to the first registered submodule, bypassing any intended overview page. By introducing an explicit "Overview" submodule and configuring it as the first entry, the change ensures that users consistently land on the overview dashboard in v13, while gracefully integrating as an additional menu item in v14 which handles overviews natively.

Highlights

  • New Overview Submodule: Introduced an admin_vault_overview submodule to serve as the initial landing page for the admin_vault parent module.
  • Module Menu Positioning: Configured the new overview submodule to appear first in the module menu using position => ['before' => '*'].
  • TYPO3 v13 Compatibility: Ensured TYPO3 v13 users are redirected to the Overview page when clicking the parent module, addressing the native redirect behavior that previously sent them to the Secrets submodule.
  • Parent Module Update: Updated the admin_vault parent module from 'admin' to 'tools' for improved TYPO3 v13 and v14 compatibility.
Changelog
  • Configuration/Backend/Modules.php
    • Changed the parent of the admin_vault module from admin to tools for better version compatibility.
    • Added a new admin_vault_overview submodule definition, setting its position to appear before all other submodules.
  • Resources/Private/Language/Modules/overview_submodule.xlf
    • Added a new XLIFF language file to provide labels and descriptions for the admin_vault_overview submodule.
Activity
  • CybotTM provided a detailed summary outlining the purpose and impact of the changes.
  • CybotTM explained the problem being solved, specifically the TYPO3 v13 module redirection behavior.
  • CybotTM included a comprehensive test plan for verifying the fix across TYPO3 v13 and v14.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated approval for solo maintainer project

This PR has passed all automated quality gates:

  • ✅ Static analysis (PHPStan)
  • ✅ Code style (PHP-CS-Fixer)
  • ✅ Unit & functional tests
  • ✅ Security scanning
  • ✅ Dependency review

See SECURITY_CONTROLS.md for compensating controls documentation.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 1, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a compatibility fix for TYPO3 v13 by adding an explicit 'Overview' submodule. This ensures that users are directed to the overview page by default, which is a good solution for the behavior of dependsOnSubmodules in v13. The changes are well-commented and clearly explained. I have one suggestion to conditionally register this new submodule to improve long-term maintainability and avoid redundancy in newer TYPO3 versions.

@CybotTM CybotTM merged commit b52b6fa into main Mar 2, 2026
129 of 132 checks passed
@CybotTM CybotTM deleted the fix/v13-module-overview branch March 2, 2026 02:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant